Serveur d'exploration sur la recherche en informatique en Lorraine

Attention, ce site est en cours de développement !
Attention, site généré par des moyens informatiques à partir de corpus bruts.
Les informations ne sont donc pas validées.

Terminology standards at work: exploring several scenarios to implement ISO 16642

Identifieur interne : 006E72 ( Main/Exploration ); précédent : 006E71; suivant : 006E73

Terminology standards at work: exploring several scenarios to implement ISO 16642

Auteurs : Laurent Romary [France] ; Isabelle Kramer ; Philippe Sébire

Source :

RBID : Hal:inria-00110779

Abstract

There is always some distance between the technical constraints that are expressed in an international standard and the actual usage an implementer can make out of them in the practical settings of its company or institution. This is all the more true for ISO 16642 (Computer applications in Terminology Terminology Markup Framework), which does not provide one single computer format for representing computerized terminologies, but rather focuses on the underlying model that any such format should be conformant with. As a consequence, it is essential to make further studies on how specific usage scenarios may lead to even more constraints on the possible data models, so that general trends can be identified and, possibly, made explicit as recommendations to the final-end users. One possible format for such recommendations will of course be the identification of data category selections (DCS) that may characterize families of interoperable data structures on the basis of the set of data categories made available by ISO standard 12620 (Computer applications in Terminology Data Categories). In this context, our paper will explore three particular situations that will be qualified according to the condition of production or consumption of terminological data, and accordingly for which the core of a possible standard DCS will be described. The three situations are the following ones: - the unification of several thesauri and term banks within a nationwide scientific documentation center; - the initial deployment of a terminology component within a large industrial group; - the definition of a pivot representation for terminology extraction components that can transparently articulate the output of such software with higher level knowledge management components. As we shall see, the flexibility offered by ISO 16642 as well as its sound principles allow us to carry such specification tasks without precluding any further evolution in those various applicative contexts. We will also see how the methodology outlined in this paper allows us to provide wider information architectures combining two or more of the scenarios that we have identified.

Url:


Affiliations:


Links toward previous steps (curation, corpus...)


Le document en format XML

<record>
<TEI>
<teiHeader>
<fileDesc>
<titleStmt>
<title xml:lang="en">Terminology standards at work: exploring several scenarios to implement ISO 16642</title>
<author>
<name sortKey="Romary, Laurent" sort="Romary, Laurent" uniqKey="Romary L" first="Laurent" last="Romary">Laurent Romary</name>
<affiliation wicri:level="1">
<hal:affiliation type="researchteam" xml:id="struct-2351" status="OLD">
<idno type="RNSR">199421391G</idno>
<orgName>Human-machine dialogue with a significant language component</orgName>
<orgName type="acronym">LANGUE ET DIALOGUE</orgName>
<desc>
<address>
<country key="FR"></country>
</address>
</desc>
<listRelation>
<relation active="#struct-160" type="direct"></relation>
<relation name="UMR7503" active="#struct-441569" type="indirect"></relation>
<relation active="#struct-300009" type="indirect"></relation>
<relation active="#struct-300291" type="indirect"></relation>
<relation active="#struct-300292" type="indirect"></relation>
<relation active="#struct-300293" type="indirect"></relation>
<relation active="#struct-2496" type="direct"></relation>
</listRelation>
<tutelles>
<tutelle active="#struct-160" type="direct">
<org type="laboratory" xml:id="struct-160" status="OLD">
<orgName>Laboratoire Lorrain de Recherche en Informatique et ses Applications</orgName>
<orgName type="acronym">LORIA</orgName>
<desc>
<address>
<addrLine>Campus Scientifique BP 239 54506 Vandoeuvre-lès-Nancy Cedex</addrLine>
<country key="FR"></country>
</address>
<ref type="url">http://www.loria.fr</ref>
</desc>
<listRelation>
<relation name="UMR7503" active="#struct-441569" type="direct"></relation>
<relation active="#struct-300009" type="direct"></relation>
<relation active="#struct-300291" type="direct"></relation>
<relation active="#struct-300292" type="direct"></relation>
<relation active="#struct-300293" type="direct"></relation>
</listRelation>
</org>
</tutelle>
<tutelle name="UMR7503" active="#struct-441569" type="indirect">
<org type="institution" xml:id="struct-441569" status="VALID">
<idno type="ISNI">0000000122597504</idno>
<idno type="IdRef">02636817X</idno>
<orgName>Centre National de la Recherche Scientifique</orgName>
<orgName type="acronym">CNRS</orgName>
<date type="start">1939-10-19</date>
<desc>
<address>
<country key="FR"></country>
</address>
<ref type="url">http://www.cnrs.fr/</ref>
</desc>
</org>
</tutelle>
<tutelle active="#struct-300009" type="indirect">
<org type="institution" xml:id="struct-300009" status="VALID">
<orgName>Institut National de Recherche en Informatique et en Automatique</orgName>
<orgName type="acronym">Inria</orgName>
<desc>
<address>
<addrLine>Domaine de VoluceauRocquencourt - BP 10578153 Le Chesnay Cedex</addrLine>
<country key="FR"></country>
</address>
<ref type="url">http://www.inria.fr/en/</ref>
</desc>
</org>
</tutelle>
<tutelle active="#struct-300291" type="indirect">
<org type="institution" xml:id="struct-300291" status="OLD">
<orgName>Université Henri Poincaré - Nancy 1</orgName>
<orgName type="acronym">UHP</orgName>
<date type="end">2011-12-31</date>
<desc>
<address>
<addrLine>24-30 rue Lionnois, BP 60120, 54 003 NANCY cedex, France</addrLine>
<country key="FR"></country>
</address>
</desc>
</org>
</tutelle>
<tutelle active="#struct-300292" type="indirect">
<org type="institution" xml:id="struct-300292" status="OLD">
<orgName>Université Nancy 2</orgName>
<date type="end">2011-12-31</date>
<desc>
<address>
<addrLine>91 avenue de la Libération, BP 454, 54001 Nancy cedex</addrLine>
<country key="FR"></country>
</address>
</desc>
</org>
</tutelle>
<tutelle active="#struct-300293" type="indirect">
<org type="institution" xml:id="struct-300293" status="OLD">
<orgName>Institut National Polytechnique de Lorraine</orgName>
<orgName type="acronym">INPL</orgName>
<date type="end">2011-12-31</date>
<desc>
<address>
<country key="FR"></country>
</address>
</desc>
</org>
</tutelle>
<tutelle active="#struct-2496" type="direct">
<org type="laboratory" xml:id="struct-2496" status="OLD">
<orgName>INRIA Lorraine</orgName>
<desc>
<address>
<addrLine>615 rue du Jardin Botanique 54600 Villers-lès-Nancy</addrLine>
<country key="FR"></country>
</address>
<ref type="url">http://www.inria.fr/centre-de-recherche-inria/nancy-grand-est</ref>
</desc>
<listRelation>
<relation active="#struct-300009" type="direct"></relation>
</listRelation>
</org>
</tutelle>
</tutelles>
</hal:affiliation>
<country>France</country>
<placeName>
<settlement type="city">Nancy</settlement>
<region type="region" nuts="2">Grand Est</region>
<region type="old region" nuts="2">Lorraine (région)</region>
</placeName>
<orgName type="university">Université Nancy 2</orgName>
<orgName type="institution" wicri:auto="newGroup">Université de Lorraine</orgName>
<placeName>
<settlement type="city">Nancy</settlement>
<region type="region" nuts="2">Grand Est</region>
<region type="old region" nuts="2">Lorraine (région)</region>
</placeName>
<orgName type="university">Institut national polytechnique de Lorraine</orgName>
<orgName type="institution" wicri:auto="newGroup">Université de Lorraine</orgName>
</affiliation>
</author>
<author>
<name sortKey="Kramer, Isabelle" sort="Kramer, Isabelle" uniqKey="Kramer I" first="Isabelle" last="Kramer">Isabelle Kramer</name>
</author>
<author>
<name sortKey="Sebire, Philippe" sort="Sebire, Philippe" uniqKey="Sebire P" first="Philippe" last="Sébire">Philippe Sébire</name>
</author>
</titleStmt>
<publicationStmt>
<idno type="wicri:source">HAL</idno>
<idno type="RBID">Hal:inria-00110779</idno>
<idno type="halId">inria-00110779</idno>
<idno type="halUri">https://hal.inria.fr/inria-00110779</idno>
<idno type="url">https://hal.inria.fr/inria-00110779</idno>
<date when="2004">2004</date>
<idno type="wicri:Area/Hal/Corpus">004A57</idno>
<idno type="wicri:Area/Hal/Curation">004A57</idno>
<idno type="wicri:Area/Hal/Checkpoint">004C92</idno>
<idno type="wicri:explorRef" wicri:stream="Hal" wicri:step="Checkpoint">004C92</idno>
<idno type="wicri:Area/Main/Merge">007242</idno>
<idno type="wicri:Area/Main/Curation">006E72</idno>
<idno type="wicri:Area/Main/Exploration">006E72</idno>
</publicationStmt>
<sourceDesc>
<biblStruct>
<analytic>
<title xml:lang="en">Terminology standards at work: exploring several scenarios to implement ISO 16642</title>
<author>
<name sortKey="Romary, Laurent" sort="Romary, Laurent" uniqKey="Romary L" first="Laurent" last="Romary">Laurent Romary</name>
<affiliation wicri:level="1">
<hal:affiliation type="researchteam" xml:id="struct-2351" status="OLD">
<idno type="RNSR">199421391G</idno>
<orgName>Human-machine dialogue with a significant language component</orgName>
<orgName type="acronym">LANGUE ET DIALOGUE</orgName>
<desc>
<address>
<country key="FR"></country>
</address>
</desc>
<listRelation>
<relation active="#struct-160" type="direct"></relation>
<relation name="UMR7503" active="#struct-441569" type="indirect"></relation>
<relation active="#struct-300009" type="indirect"></relation>
<relation active="#struct-300291" type="indirect"></relation>
<relation active="#struct-300292" type="indirect"></relation>
<relation active="#struct-300293" type="indirect"></relation>
<relation active="#struct-2496" type="direct"></relation>
</listRelation>
<tutelles>
<tutelle active="#struct-160" type="direct">
<org type="laboratory" xml:id="struct-160" status="OLD">
<orgName>Laboratoire Lorrain de Recherche en Informatique et ses Applications</orgName>
<orgName type="acronym">LORIA</orgName>
<desc>
<address>
<addrLine>Campus Scientifique BP 239 54506 Vandoeuvre-lès-Nancy Cedex</addrLine>
<country key="FR"></country>
</address>
<ref type="url">http://www.loria.fr</ref>
</desc>
<listRelation>
<relation name="UMR7503" active="#struct-441569" type="direct"></relation>
<relation active="#struct-300009" type="direct"></relation>
<relation active="#struct-300291" type="direct"></relation>
<relation active="#struct-300292" type="direct"></relation>
<relation active="#struct-300293" type="direct"></relation>
</listRelation>
</org>
</tutelle>
<tutelle name="UMR7503" active="#struct-441569" type="indirect">
<org type="institution" xml:id="struct-441569" status="VALID">
<idno type="ISNI">0000000122597504</idno>
<idno type="IdRef">02636817X</idno>
<orgName>Centre National de la Recherche Scientifique</orgName>
<orgName type="acronym">CNRS</orgName>
<date type="start">1939-10-19</date>
<desc>
<address>
<country key="FR"></country>
</address>
<ref type="url">http://www.cnrs.fr/</ref>
</desc>
</org>
</tutelle>
<tutelle active="#struct-300009" type="indirect">
<org type="institution" xml:id="struct-300009" status="VALID">
<orgName>Institut National de Recherche en Informatique et en Automatique</orgName>
<orgName type="acronym">Inria</orgName>
<desc>
<address>
<addrLine>Domaine de VoluceauRocquencourt - BP 10578153 Le Chesnay Cedex</addrLine>
<country key="FR"></country>
</address>
<ref type="url">http://www.inria.fr/en/</ref>
</desc>
</org>
</tutelle>
<tutelle active="#struct-300291" type="indirect">
<org type="institution" xml:id="struct-300291" status="OLD">
<orgName>Université Henri Poincaré - Nancy 1</orgName>
<orgName type="acronym">UHP</orgName>
<date type="end">2011-12-31</date>
<desc>
<address>
<addrLine>24-30 rue Lionnois, BP 60120, 54 003 NANCY cedex, France</addrLine>
<country key="FR"></country>
</address>
</desc>
</org>
</tutelle>
<tutelle active="#struct-300292" type="indirect">
<org type="institution" xml:id="struct-300292" status="OLD">
<orgName>Université Nancy 2</orgName>
<date type="end">2011-12-31</date>
<desc>
<address>
<addrLine>91 avenue de la Libération, BP 454, 54001 Nancy cedex</addrLine>
<country key="FR"></country>
</address>
</desc>
</org>
</tutelle>
<tutelle active="#struct-300293" type="indirect">
<org type="institution" xml:id="struct-300293" status="OLD">
<orgName>Institut National Polytechnique de Lorraine</orgName>
<orgName type="acronym">INPL</orgName>
<date type="end">2011-12-31</date>
<desc>
<address>
<country key="FR"></country>
</address>
</desc>
</org>
</tutelle>
<tutelle active="#struct-2496" type="direct">
<org type="laboratory" xml:id="struct-2496" status="OLD">
<orgName>INRIA Lorraine</orgName>
<desc>
<address>
<addrLine>615 rue du Jardin Botanique 54600 Villers-lès-Nancy</addrLine>
<country key="FR"></country>
</address>
<ref type="url">http://www.inria.fr/centre-de-recherche-inria/nancy-grand-est</ref>
</desc>
<listRelation>
<relation active="#struct-300009" type="direct"></relation>
</listRelation>
</org>
</tutelle>
</tutelles>
</hal:affiliation>
<country>France</country>
<placeName>
<settlement type="city">Nancy</settlement>
<region type="region" nuts="2">Grand Est</region>
<region type="old region" nuts="2">Lorraine (région)</region>
</placeName>
<orgName type="university">Université Nancy 2</orgName>
<orgName type="institution" wicri:auto="newGroup">Université de Lorraine</orgName>
<placeName>
<settlement type="city">Nancy</settlement>
<region type="region" nuts="2">Grand Est</region>
<region type="old region" nuts="2">Lorraine (région)</region>
</placeName>
<orgName type="university">Institut national polytechnique de Lorraine</orgName>
<orgName type="institution" wicri:auto="newGroup">Université de Lorraine</orgName>
</affiliation>
</author>
<author>
<name sortKey="Kramer, Isabelle" sort="Kramer, Isabelle" uniqKey="Kramer I" first="Isabelle" last="Kramer">Isabelle Kramer</name>
</author>
<author>
<name sortKey="Sebire, Philippe" sort="Sebire, Philippe" uniqKey="Sebire P" first="Philippe" last="Sébire">Philippe Sébire</name>
</author>
</analytic>
</biblStruct>
</sourceDesc>
</fileDesc>
<profileDesc>
<textClass>
<keywords scheme="mix" xml:lang="it">
<term>iso 16642</term>
<term>normalisation</term>
<term>standardization</term>
<term>terminologie</term>
<term>terminology</term>
</keywords>
</textClass>
</profileDesc>
</teiHeader>
<front>
<div type="abstract" xml:lang="en">There is always some distance between the technical constraints that are expressed in an international standard and the actual usage an implementer can make out of them in the practical settings of its company or institution. This is all the more true for ISO 16642 (Computer applications in Terminology Terminology Markup Framework), which does not provide one single computer format for representing computerized terminologies, but rather focuses on the underlying model that any such format should be conformant with. As a consequence, it is essential to make further studies on how specific usage scenarios may lead to even more constraints on the possible data models, so that general trends can be identified and, possibly, made explicit as recommendations to the final-end users. One possible format for such recommendations will of course be the identification of data category selections (DCS) that may characterize families of interoperable data structures on the basis of the set of data categories made available by ISO standard 12620 (Computer applications in Terminology Data Categories). In this context, our paper will explore three particular situations that will be qualified according to the condition of production or consumption of terminological data, and accordingly for which the core of a possible standard DCS will be described. The three situations are the following ones: - the unification of several thesauri and term banks within a nationwide scientific documentation center; - the initial deployment of a terminology component within a large industrial group; - the definition of a pivot representation for terminology extraction components that can transparently articulate the output of such software with higher level knowledge management components. As we shall see, the flexibility offered by ISO 16642 as well as its sound principles allow us to carry such specification tasks without precluding any further evolution in those various applicative contexts. We will also see how the methodology outlined in this paper allows us to provide wider information architectures combining two or more of the scenarios that we have identified.</div>
</front>
</TEI>
<affiliations>
<list>
<country>
<li>France</li>
</country>
<region>
<li>Grand Est</li>
<li>Lorraine (région)</li>
</region>
<settlement>
<li>Nancy</li>
</settlement>
<orgName>
<li>Institut national polytechnique de Lorraine</li>
<li>Université Nancy 2</li>
<li>Université de Lorraine</li>
</orgName>
</list>
<tree>
<noCountry>
<name sortKey="Kramer, Isabelle" sort="Kramer, Isabelle" uniqKey="Kramer I" first="Isabelle" last="Kramer">Isabelle Kramer</name>
<name sortKey="Sebire, Philippe" sort="Sebire, Philippe" uniqKey="Sebire P" first="Philippe" last="Sébire">Philippe Sébire</name>
</noCountry>
<country name="France">
<region name="Grand Est">
<name sortKey="Romary, Laurent" sort="Romary, Laurent" uniqKey="Romary L" first="Laurent" last="Romary">Laurent Romary</name>
</region>
</country>
</tree>
</affiliations>
</record>

Pour manipuler ce document sous Unix (Dilib)

EXPLOR_STEP=$WICRI_ROOT/Wicri/Lorraine/explor/InforLorV4/Data/Main/Exploration
HfdSelect -h $EXPLOR_STEP/biblio.hfd -nk 006E72 | SxmlIndent | more

Ou

HfdSelect -h $EXPLOR_AREA/Data/Main/Exploration/biblio.hfd -nk 006E72 | SxmlIndent | more

Pour mettre un lien sur cette page dans le réseau Wicri

{{Explor lien
   |wiki=    Wicri/Lorraine
   |area=    InforLorV4
   |flux=    Main
   |étape=   Exploration
   |type=    RBID
   |clé=     Hal:inria-00110779
   |texte=   Terminology standards at work: exploring several scenarios to implement ISO 16642
}}

Wicri

This area was generated with Dilib version V0.6.33.
Data generation: Mon Jun 10 21:56:28 2019. Site generation: Fri Feb 25 15:29:27 2022